

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Software Architects [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Project Role,Project Role Software Architect,Software Architect,Software Architect Project Role,Software Architect And Enterprise Architect,Enterprise Architect,Enterprise Architect For Software Architects">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Software Architects</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="businessanalyst.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="softwareengineer.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">Software Architects can use Enterprise Architect to map functional requirements with Use Cases, perform real time modeling of objects using </span><span class="f_BodyText" style="font-style: italic;">Interaction diagrams</span><span class="f_BodyText"> (<a href="denotelifecycleofanelement.htm">Sequence</a>, <a href="timingdiagram.htm">Timing</a>, <a href="communicationdiagram.htm">Communication</a> or <a href="interactionoverviewdiagram.htm">Interaction Overview</a>), design the <a href="deploymentdiagram.htm">Deployment</a> model and detail the deliverable components using <a href="componentdiagram.htm">Component</a> diagrams.</span></p>
<p class="p_TextIndentedL2"><img src="sequencediagram.png" width="813" height="597" border="0" alt="SequenceDiagram"></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Map Functional Requirements of the System</span></p>
<p class="p_BodyText"><span class="f_BodyText">With Enterprise Architect the Software Architect can take the high level business processes that have been modeled by the Business Analyst and create detailed <a href="usecase.htm">Use Cases</a>. Use Cases are used to describe the proposed functionality of a system and are only used to detail a single unit of discrete work.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Map Objects in Real Time</span></p>
<p class="p_BodyText"><span class="f_BodyText">The Software Architect can use Interaction diagrams (<a href="sequencediagram.htm">Sequence</a> and <a href="communicationdiagram.htm">Communication</a> diagrams) to model the dynamic design of the system. Sequence diagrams are used to detail the messages that are passed between objects and the lifetimes of the objects. Communication diagrams are similar to Sequence diagrams, but are used instead to display the way in which the object interacts with other objects.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Map Deployment of Objects</span></p>
<p class="p_BodyText"><span class="f_BodyText">The Software Architect can use <a href="deploymentdiagram.htm">Deployment diagrams</a> to provide a static view of the run-time configuration of processing nodes and the components that run on the nodes. Deployment diagrams can be used to show the connections between hardware, software and any middleware that is used on a system.</span></p>
<p class="p_SubHeadingL1"><span class="f_SubHeadingL1">Detail Deliverable Components</span></p>
<p class="p_BodyText"><span class="f_BodyText"><a href="componentdiagram.htm">Component diagrams</a> enable the Software Architect to model the physical aspects of a system. Components can be executables, libraries, data files or another physical resource that is part of a system. The component model can be developed from scratch from the Class model or can be brought in from existing projects and from third-party vendors.</span></p>
<p class="p_SeeAlso"><span class="f_SeeAlso">See Also</span></p>
<ul style="text-indent: 0px; margin-left: 30px; list-style-position: outside;">
<li><span class="f_Bulletlist1"><a href="analysisdiagram.htm">Analysis Diagrams</a></span></li>
<li><span class="f_Bulletlist1" style="font-style: italic;"><a href="uml.htm">Modeling with UML</a></span></li>
<li><span class="f_Bulletlist1" style="font-style: italic;"><a href="importexport.htm">XMI Import and Export</a></span></li>
<li><span class="f_Bulletlist1" style="font-style: italic;"><a href="xml_technologies.htm">XML Technologies</a></span></li>
</ul>




            </div>
          </div>
        </div>



</div>


</body>
</html>
